Summary

This PR decouples the [discord] section generation in config.toml from the presence of botToken at render time.

Problem

Previously, the [discord] block would only be generated if a botToken was provided to Helm. This forced users who manage secrets at runtime (e.g., via AWS Secrets Manager) to either:

1. Provide a dummy token to Helm (confusing).
2. Provide the real token to Helm (security risk, as it's stored in Helm history).

Solution

The template now only checks for ($cfg.discord).enabled. This allows the block to be generated while relying on runtime environment variable expansion (${DISCORD_BOT_TOKEN}) for the actual authentication.

Context

• Fixes [Bug] [Helm] Helm chart 0.7.7-beta.1: [discord] section in config.toml depends on botToken being set at render time #392
• Discord discussion: https://discord.com/channels/1491295327620169908/1491365162869985283
• Reference: feat(helm): add pod extensibility controls #380